Motivation

Previously Workflow Runs tab has implemented and placed in CI/CD menu. Now, Workflow Run Detail page is added to see Jobs, Tests (if exists). Additionally, Helios was not supporting re-run a workflow and re-run failed jobs features before. Also, cancellation a deployment was possible but we didn't have cancel workflow functionality. Now, these three options are also added to Workflow Run Detail page. This PR is related to these issue: #913 #918

Description

This PR introduces end-to-end workflow run details support and action handling across backend and frontend.

• Added backend API endpoints for:
  • fetching workflow run details by run ID,
  • canceling a workflow run,
  • re-running all jobs in a workflow run,
  • re-running failed jobs only,
  • fetching test results by workflow run ID.
• Extended GitHub integration service to execute workflow run actions (cancel, rerun, rerun-failed-jobs) with shared error handling.
• Added a dedicated Workflow Run Details page and route.
• Enhanced workflow runs table UX:
  • row click navigation to run details,
  • clearer columns (test processing, duration),
  • improved date/time display.
• Refactored workflow jobs rendering:
  • extracted reusable workflow-job-list component,
  • reused it in environments and run-details views.
• Extended pipeline test results selection to support workflowRunId.
• Improved run-details polling after action triggers, so delayed GitHub synchronization can still be reflected in the UI without manual refresh.

Testing Instructions

Prerequisites:

• GitHub account with normal developer access (no admin/owner permissions required).
• A repository connected in Helios with existing workflow runs.
• At least one completed workflow run (preferably one failed run to test “Re-run failed”)

Flow:

1. Log in to Helios as a Developer with write access
2. Open a repository and navigate to CI/CD > Workflow Runs.
3. Open a failed workflow run details page that includes test cases.
4. On the details page, verify baseline data:

• run title/status/branch/SHA/timestamps are visible,
• jobs list is rendered,
• test results section loads for test-labeled runs.

5. Trigger actions:

• click Re-run All on a completed run,
• click Re-run Failed on a failed run,
• click Cancel on an active run.

6. Confirm behavior after each action:

• success toast appears,
• page updates status/jobs without hard refresh,
• delayed GitHub sync is eventually reflected (allow up to ~2 minutes).

9. Logout or login with readonly access.
10. Verify that Jobs component and re-run/cancel buttons are not visible.

Screenshots

Checklist

General

• PR description explains the purpose and changes. (f.e. following the 'Conventional Commits')
• Changes have been tested locally.
• Screenshots have been attached.

Server

• Code is performant and follows best practices
• I documented the Java code using JavaDoc style.

Client

• I documented the TypeScript code using JSDoc style.
• I added multiple screenshots/screencasts of my UI changes.